Apparatus and methods for telecommunication authentication

ABSTRACT

The present invention is related to telecommunications, and in particular to systems and methods of using telecommunication services for user authentication. Account information is stored for a user, the account information including at least a first phone number associated with the user. A user order is received. A verification phone call is received from the user, the call including charge phone number information. The charge number information is compared to the first phone number to authenticate that the user is associated with the first phone number. Based at least in part on the comparison, the user order is selectively caused to be fulfilled.

PRIORITY CLAIM

This application is a continuation of U.S. application Ser. No. 12/275,138, filed Nov. 20, 2008, which is a continuation of U.S. application Ser. No. 10/385,204, filed Mar. 7, 2003, now U.S. Pat. No. 7,460,653, which are hereby incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is related to telecommunications, and in particular to systems and methods of using telecommunication services for user authentication.

2. Description of the Related Art

As orders for services and products are increasingly made by phone or via the Internet, the opportunity for users to commit pranks and fraud has likewise increased. For example, one prank is to instruct a call processing service to have calls to the victim forwarded to another number. These pranks can be both annoying and expensive, and can reach the level of fraud or “cramming.” Cramming occurs when a subscriber is billed for phone related services that the subscriber did not request, such as voice mail, paging, 900 number calls, and pay-per-call 800 numbers.

SUMMARY OF THE INVENTION

Embodiments of the present invention utilize telecommunication services to reduce the success of frauds, pranks and cramming, and to verify that orders for goods and services are legitimate. Thus, for example, embodiments of the present invention authenticate and verify that a user is associated with a phone number provided by the user when placing an order or when establishing an account. If the authentication or verification fails, the order can be rejected, thereby advantageously reducing the fulfillment of fraudulent orders or prank orders and further reducing the incidences of successful cramming.

One embodiment is a method of authenticating a user identity using telephony signaling, comprising: storing account information for a user, the account information including at least a first phone number associated with the user; receiving a user order; receiving a call from the user, the call including charge phone number information; comparing the charge number information with the stored first phone number to authenticate that the user is associated with the first phone number; and based at least in part on the comparison, selectively causing the user order to be fulfilled.

Another embodiment is a method of authenticating a user identity using telephony signaling, comprising: receiving from a first user a call handling instruction for calls placed to a first telephone number; causing a computer terminal associated with the first user to place a call to a second telephone number, the call including corresponding call signaling information; receiving the call and corresponding call signaling information; comparing at least a portion of the corresponding call signaling information with the first telephone number; and based at least in part on the comparison, determining if the call instruction is to be complied with.

Still another embodiment is a method of authenticating a caller identity using SS7 signaling, comprising: receiving a user order for at least one of a good and a service; requesting that the user provide a phone number associated with a first telephone line; instructing a client application executing on a user computer to initiate a call to a call processing system, the call associated with SS7 signaling information including caller-ID information and charge number information, wherein the user computer places the call using the first telephone line; verifying that at least one of the caller-ID information and charge number information corresponds to the phone number provided by the user; and providing the at least one of a good and a service at least partly in response to verifying that at least one of the caller-ID information and charge number information corresponds to the phone number provided by the user.

Yet another embodiment is a method of processing telephony signaling information, comprising: receiving a user order; requesting that the user provide a phone number associated with a first telephone line; initiating a call using the first telephone line to a call processing system, the call associated with signaling information including charge number information; verifying that the charge number information corresponds to the phone number provided by the user; and complying with the order at least partly in response to verifying that the charge number information corresponds to the phone number provided by the user.

One embodiment is a method of authenticating a caller identity using SS7 signaling, comprising: receiving a user request over the Internet via a computer terminal associated with the user, wherein the computer terminal is accessing the Internet using a first telephone line; causing the computer terminal to cease accessing the Internet using the first telephone line; causing the computer terminal to call a first telephone number using the first telephone line; receiving the call and corresponding signaling information, wherein the signaling information includes a phone number associated with the first telephone line; and at least partly in response to the signaling information, selectively responding to the user request.

Another embodiment is a method of processing telephony signaling information, comprising: receiving a request for a password from a user; requesting that the user call a first phone number in response to receiving the user request; receiving a call from the user to the first phone number, the call including signaling information; verifying that the call originated from the user based at least in part on the signaling information; and providing the user with the password at least partly in response to verifying that the call originated from the caller.

Still another embodiment is a method of verifying a user identity, comprising: receiving from a first user a phone service instruction related to a first telephone number; providing to the first user a verification code via a computer terminal associated with the first user; causing a verification instruction to be provided to the first user, wherein the verification instruction includes an instruction to call a second telephone number and to enter the verification code; receiving a call, including call signaling information, and the verification code from the first user; comparing at least a portion of the call signaling information with the first telephone number; and at least partly in response to the comparison, determining whether to cause the phone service instruction to be complied with.

Yet another embodiment is a method of verifying a user identity, comprising: receiving from a first user a phone service instruction for calls placed to a first telephone number, wherein the first user provided the phone service instruction via a client application executing on an online computer terminal, and the online computer terminal is online via a telephone line associated with the first telephone number; transmitting a first code to the first user via the online computer terminal; informing the first user that a call will be placed to the first user and that the first user is to provide the first code during the call; causing the computer terminal to go offline; placing the call to the first telephone number; receiving a code entry from the first user during the call; comparing the code entry to the first code; and at least partly in response to the comparison, determining if the phone service instruction is to be executed.

One embodiment is a method of verifying a user identity, comprising: receiving from a first user a phone service instruction for a first telephone number, wherein the first user provided the phone service instruction via a client application executing on an online computer terminal, and the online computer terminal is online via a telephone line associated with the first telephone number; transmitting a first code to the first user via the online computer terminal; requesting the caller to call a second telephone number and to provide the first code during the call; receiving the user call to the second telephone phone number; receiving a code entry from the first user during the call; comparing the code entry to the first code; and at least partly in response to the comparison, determining if the phone service instruction is to be executed.

Another embodiment is an apparatus for authenticating a user identity using telephony signaling, comprising: a first computer readable memory storing account information for a user, the account information including at least a first phone number associated with the user; a first instruction configured to receive a user order; a second instruction configured to receive a call from the user, the call including charge phone number information; and a third instruction configured to compare the charge number information to the first phone number to authenticate that the user is associated with the first phone number, and based at least in part on the comparison, selectively causing the user order to be fulfilled.

Yet another embodiment is an authentication apparatus, comprising: a PSTN interface; a data network interface; and a call processing system configured to: receive via the data network interface a phone service instruction for to a first telephone number account from a first user; cause a user computer terminal to place a call to a second telephone number, the call including corresponding call signaling information; receive the call and corresponding call signaling information via the PSTN interface; compare at least a portion of the corresponding call signaling information with the first telephone number; and based at least in part on the comparison, determine if the call instruction is to be complied with.

Still another embodiment is an apparatus for verifying a user identity, comprising: a PSTN interface; a data network interface; and a call processing system configured to: receive via the PSTN interface from a first user computer terminal a call handling instruction for calls placed to a first telephone number; transmit a first code to the first user via the computer terminal; inform the first user that a call will be placed to the first user and that the first user is to provide the first code during the call; place the call to an account telephone number provided by the first user; receive a code entry from the first user during the call; compare the code entry to the first code; at least partly in response to the comparison, determine if the call handling instruction is to be executed.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are described herein with reference to the drawings summarized below. These drawings and the associated description are provided to illustrate example embodiments of the invention, and not to limit the scope of the invention.

FIG. 1 illustrates an example telecommunications system that can be used in accordance with one embodiment of the present invention.

FIG. 2 further details subsystems included in the call processing system depicted in FIG. 1.

FIGS. 3A-D illustrate example authentication processes wherein a call is placed from a user's phone line.

FIG. 4 illustrates an example authentication process wherein a call is placed to a user's phone line.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention is related to telecommunications, and in particular to using telecommunication services for user authentication. Embodiments of the present invention enable the authentication of users placing orders for goods and services using a telecommunications network and/or a data network.

Throughout the following description, the term “Web site” is used to refer to a user-accessible network site that implements the basic World Wide Web standards for the coding and transmission of hypertextual documents. These standards currently include HTML (the Hypertext Markup Language) and HTTP (the Hypertext Transfer Protocol). It should be understood that the term “site” is not intended to imply a single geographic location, as a Web or other network site can, for example, include multiple geographically distributed computer systems that are appropriately linked together. Furthermore, while the following description relates to an embodiment utilizing the Internet and related protocols, other networks, such as networked interactive televisions, and other protocols may be used as well. In addition, unless otherwise indicated, the functions described herein are preferably performed by executable code and instructions running on one or more general-purpose computers. However, the present invention can also be implemented using special purpose computers, state machines, and/or hardwired electronic circuits.

As described in greater detail below, in one embodiment, when a user is ordering phone services associated with a first phone number, as part of a verification process, the user calls a designated verification phone number. The call's charge number information is obtained by accessing signaling information, such as SS7 signaling information, to verify that the call originated from a phone line associated with the first phone number. Using the charge number for verification purposes has significant advantages as compared to using a call's Caller ID (CID) information for verification purposes. In one series of tests, 10 to 15 percent of calls to a toll-free number did not have CID information, while almost 100% of the calls did have the charge number information. Thus, the charge number obtained through network signaling is a more reliable method of verifying that a call originated from a particular number.

FIG. 1 illustrates an example telecommunications system that can be used in accordance with the present invention. As illustrated, the telecommunications system includes:

-   -   a user telephone station 112.     -   an optional user computer terminal 110.     -   a call processing system 124, that provides call processing and         answering services.     -   a communications management client software application 116. The         client application 116 dials numbers using computer terminal 110         hardware, communicates with the call processing system 124 via         the Internet 106 and/or other computer networks, provides a user         interface with which the user can provide instructions, and         provides the user with information from the call processing         system 124.

In this example, these devices are linked together using line and trunk circuits to a Public Switched Network (PSTN) 104 and to a common data network, such as the Internet 106 or other Internet Protocol (IP) network.

Referring back to FIG. 1, in this example the telephone station 112 is connected to local exchange switch (LEC) 126 via telephone line 114. The user telephone station 112 can optionally be a conventional POTS (Plain Old Telephone Service) telephone or, in certain embodiments, a local extension behind a corporate Private Branch Exchange (PBX).

In this example, the Local Exchange Carrier (LEC) switch 126 is coupled to Inter Exchange Carrier's (IXC) circuit switched or packet switched telephony network 102. As illustrated in FIGS. 1 and 2, the call processing system is coupled to the Internet 106 via trunk or line 142.

The telephone line 114 can optionally be shared with one or more computer terminals. For example, telephone terminal 112 shares the telephone line 114 with the computer terminal 110. While in the illustrated example the computer terminal 110 is a personal computer, the computer terminal 110 can be an interactive television, a networked-enabled personal digital assistant (PDA), other IP (Internet Protocol) device, or the like. In the illustrated embodiment, the computer terminal 110 is a personal computer having a monitor, keyboard, a mouse, a disk drive, sound card or similar sound reproduction circuitry such as a codec, streaming media playback software, such as the Media Player program available from Microsoft, speakers, and a modem, such as a standard V.90 56K dial-up modem. The modem can optionally be configured to dial-up a number under control of an application, such as a contact manager application or telecommunications client application 116, stored and executing on the computer terminal 110.

The telephone line 114 can be used to establish a dial-up connection for computer terminals, such as terminal 110, via the computer modem to an Internet Service Provider (ISP) offering dial-in remote access service connections from the PSTN 104 via trunk interface 120. The computer terminal 110 can also be connected to the Internet 106 via a broadband connection, such as a DSL line, a television cable line, or a T1 line.

In addition, the computer terminal 110 can be equipped with a Voice over Internet Protocol (VoIP) software module and a headset or a handset 132, including a microphone and speaker, allowing voice communications to be conducted over a computer network, such as the Internet 106. VoIP communicates information via packet switching, which opens a connection just long enough to send a small packet of data. Each packet includes a destination address informing the network where to send the packet along with the actual voice data payload. If the receiving station is also a VoIP terminal, then when the receiving terminal receives the packets, VoIP software executing on the receiving terminal reassembles the packets into the original data stream. The data stream is then converted to a voice signal. If the receiving station is a conventional telephone, then a VoIP gateway converts the packets into a voice signal that is then connected to the PSTN 104.

In one embodiment, the VoIP process is performed using the H.323 standardized protocol established by the International Telecommunications Union (ITU). Advantageously, H.323 provides specifications for real-time, interactive videoconferencing, data sharing and audio applications such as IP telephony. Alternatively, the Session Initiation Protocol (SIP), established by the Internet Engineering Task Force (IETF), can be used. SIP is generally more efficient than the H.323 protocol as SIP is specifically intended for IP telephony. In addition, proprietary protocols could be deployed where multi-vendor interoperability is not needed.

FIG. 2 illustrates the call processing system 124 in greater detail:

-   -   Call Management (CM) subsystem 108, which serves as the         interface to the PSTN 104 to manage inbound and outbound         telephone calls.     -   a Router subsystem 140, which serves as the interface to the         Internet 106 to manage communications between online IP client         devices and the various call processing servers.     -   an online presence detection Internet Session Management (SM)         subsystem 122, which monitors the status of subscriber data         terminals to determine availability for call handling services.     -   a shared Media Storage (MS) subsystem 138, which persistently         archives the callers voice messages and the called         party/subscriber's personal greeting(s),     -   a call processing Database (DB) subsystem 136 in which called         party/subscriber call processing service parameters and account         information are stored.

Theses various subsystems are interconnected via a Local Area Network (LAN) and/or via a Wide Area Network (WAN).

In the illustrated embodiment, the CM subsystem 108 is coupled into the PSTN 104 through voice trunk circuits 118 directly interfacing with the Inter Exchange Carrier's (IXC) circuit switched or packet switched telephony network 102. Thus, advantageously the call processing system 124 does not have to be directly serviced by the same Local Exchange Carrier's (LEC) switch or PBX as the terminal 112. Indeed, the call processing system 124 or its individual subsystem components can be located in a different country than the station 112. In this instance, the call processing system 124 is optionally configured as, or to appear as, a telephone end office and can interface with the PSTN 104 as an end office or Class 5 switch. In other embodiments, the call processing system 124 is locally attached to a LEC switch with a physical line or local trunk interface circuit. This switch may or may not be serving the telephone station 112.

FIG. 3A illustrates an example transaction process, including an authentication process. The example authentication process can be used to verify that orders for goods or services are legitimate. In the illustrated example, the process begins at state 302 and proceeds to state 304. At state 304 using subscriber computer terminal 110, a user sets up an account with a merchant or service provider, such as a call management service provider associated with the call processing system 124. For clarity, the following example assumes that the following process is being conducted with a call management service provider, though the process can similarly be used with other providers of services and goods.

In setting up the account, the user provides a phone number that the user indicates is the user's phone number. The user can also provide other contact information, including, by way of example, an email address, a regular address, a facsimile number, alternate phone numbers, and the like, as well as a user identifier and a user password. At state 306, the user downloads a client application, such as client application 116 discussed above. At state 308 the client application 116 establishes communication with the session manager 122. For example, the client application 116 can transmit a unique identifier and an “I'm alive” message and subsequent periodic “keep alive” messages to the online presence detection Internet Session Management (SM) subsystem 122.

An order takes place at state 310. State 310 can occur during the same Internet session as the foregoing states, or during a later Internet session. In particular, at state 310 the user places an order for a good or service. For example, a user can subscribe to a call processing service, wherein the user authorizes certain call handling functions. The user can instruct that calls to the account phone number, associated with the subscriber telephone station 112, be forwarded to the call processing system 124 in response to certain conditions. The user can authorize or instruct that calls to the user phone number be forwarded to the call processing service using one or more of the following: call forwarding on busy, call forwarding on ring-no-answer, and call-forward-all calls (sometimes called do-not-disturb). When forwarded calls are received by the call processing system 124, the call processing system 124 will handle the forwarded calls in accordance with the user's instructions. For example, with respect to forwarded calls, the user can instruct the call processing system to play a message from the user to the caller and/or record a message from the caller. By way of further example, the order can be for a forgotten account password or for a product. The request to establish the account is also a type of order.

In this example, the user order is provided via the client application 116. In other examples, the order can be provided via a website, such as the call processing service provider's website, via phone, via email, via regular mail, or the like. At state 312 the session manager 122 transmits user authentication instructions to the client application 116. Before issuing the instructions, the online presence detection Internet Session Management (SM) subsystem 122 optionally first determines that the computer terminal 110 is online. In other embodiments, the user authentication instructions are transmitted to the user via email or presented to the user via a web page.

At state 314 the client application presents the instructions to the user. Alternatively or in addition, the user authentication instructions can be displayed to the user via a web page presented on the computer terminal 110 or can be transmitted to the user via email. In one embodiment, as a precondition to fulfilling the user order, the user is asked to comply with the authentication instructions so as to help stop fraud and pranks. The instructions request the caller to cause the computer terminal to go offline, that is, to stop accessing the Internet using the phone line associated with the account phone number, and to call a specified authentication or verification phone number, which can be a toll free number, using the phone line associated with the account phone number. The user can also be requested to turn Caller-ID blocking off, though if the call is being placed to an 800 number or the like, or to an end office or Class 5 switch, this is not necessary as Caller-ID blocking is not effective to block receipt of the Caller-ID information in these cases. Optionally, the instructions can provide the user with a verification password, which for example, might be an encrypted version of the user's account number or name. The user will be instructed to enter the password verbally or using the phone 112 keypad to generate DTMF tones. At state 315 the Internet session is terminated and the SM 122 automatically logs out the client application 116.

Alternatively or in addition, rather than having the user place the call, the client application 116 can determine when the computer terminal 110 has gone offline, and then places the call to the authentication or verification phone number automatically. Alternatively or in addition, the client application 116 can automatically disconnect the computer terminal from the Internet 106. If the computer terminal 110 is coupled to the Internet 106 via a broadband connection, the client application 116 or user can dial the authentication or verification phone number without having to disconnect the terminal 110 from the Internet connection.

At state 316 the user or client application 116 calls the specified authentication phone number using the phone line associated with the account phone number. If a verification password has been provided, then the user will enter the verification password. Once the call is placed, the call processing system 124 receives the call and associated call signaling. For example, embodiments of the present invention can be utilized with a Common Channel Signaling system, such as Signaling System 7 (SS7), having separate voice/user data and signaling channels. In addition, embodiments of the present invention can be used with other signaling methods, such as the following trunk-side signaling interfaces: ISDN-PRI; Advanced Intelligent Network; and/or Service Node architectures. In addition, the equivalent network signaling information can be accessed in another network. For example, the signaling information can be accessed via an Internet Telephony Network, where a gateway maps the SS7 signaling information in to an equivalent SIP/H.232 field. Thus, for example, the SS7 charge number field can be mapped into a SIP/H.232 equivalent charge number field. Similarly, an SS7 gateway can map the signaling information into other corresponding signaling protocol fields.

The signaling system can provide some or all of call presentation information discussed below to the call processing system:

-   -   ANI—Automatic Number Identification: phone number and privacy         indicator of the calling party (“CID” or “Caller-ID”), if         available.     -   DNIS—Dialed Number Identification: phone number of the call         processing system's voice trunks that the call was forwarded to.     -   OCN—Original Called Number Identification: phone number of the         original called party (subscriber to the call processing         service), if available.     -   Call Type—Forwarded call due to a BCF, RNA, or DND/CFA         condition. In addition, directly dialed inbound calls can be         handled as well. In this instance, the caller will be requested         to enter the subscriber's phone number or the subscriber could         be assigned a unique personal number that is directly dialed by         their callers.     -   CN—Charge Number; The phone number which will be charged for the         call,

At state 318, the CM 108 compares the ANI (CID) with the account phone number that had been stored in the user account database 136. In addition, if the user or client entered a verification password, via DTMF touch-tone or speech, then the entered verification password will be compared to that provided by the system 124 to the user. If at state 320 the comparison with the ANI (CID) fails, the process proceeds to state 332 and the CM 108 accesses the SS7 charge number (CN) signaling information and compares the account phone number to the CN. If the comparison with the charge phone number fails, and/or optionally if the password comparison fails, the process proceeds to state 326 and the user is informed of the failure and the order is refused, or the call is optionally transferred to a live operator, either automatically or in response to a user initiated DTMF touch-tone or voice request. If either or both the comparison to the ANI and the comparison to the charge phone number succeed, and optionally if the password comparison succeeds, then the user has been authenticated, and the process proceeds to state 328. The user's order will be fulfilled and/or instruction complied with, and the user is so notified verbally, via email, and/or via the client application 116 the next time the client application 116 has a session with the call processing system 124.

Alternatively, rather than first comparing the ANI to the claimed user's phone number, the first, and optionally only, comparison is of the charge phone number and the user's account phone number.

FIGS. 3B-3D illustrate the call flows of the example authentication embodiments discussed above with reference to FIG. 3A. FIG. 3B illustrates the authentication process wherein the user or account owner places the authentication call. At state 302B the user or account owner calls the authentication or verification phone number provided to the user as similarly discussed above with respect to FIG. 3A. At state 304B the Call Management (CM) subsystem 108 answers the call and records the charge number (CN) and optionally the ANI/Caller-ID (CID). At state 306B the CM 108 determines whether the CN is the same as the account phone number. If the CN is not the same as the account phone number, the authentication fails. If the CN is the same as the account phone number, the authentication is successful. Optionally, the ANI (CID) can also be compared with the account phone number as part of the authentication process as similarly discussed above with respect to FIG. 3A. At state 308B the CM 108 informs the user or account owner whether the authentication succeeded or failed. At state 310B the CM 108 terminates the call with the account owner.

FIG. 3C illustrates the authentication process wherein the user or account owner places the authentication call and enters a password during the call. The password is provided to the user as similarly discussed above with respect to FIG. 3A. At state 302C the user or account owner calls the authentication or verification phone number provided to the user as similarly discussed above with respect to FIG. 3A. At state 304C the Call Management (CM) subsystem 108 answers the call and records the charge number (CN) and optionally the ANI (CID). At state 306C the CM 108 determines whether the CN is the same as the account phone number. If the CN is not the same as the account phone number, the phone number authentication fails. If the CN is the same as the account phone number, the phone number authentication is successful. Optionally, the ANI (CID) can also be compared with the account phone number as part of the authentication process as similarly discussed above with respect to FIG. 3A.

At state 308C the CM 108 requests the user or account owner to enter the password using the telephone keys, which generates DTMF tones that can be recorded by the CM 108, or by speaking the password. At state 310C the user or account owner enters the password using the telephone keys or by speaking the password. At state 312C the CM 108 determines whether the password entered by the user or account owner matches that provided to the account owner and stored in the account owner's database record to thereby verify whether the entered password is correct. At state 314C the CM 108 informs the user or account owner whether the authentication succeeded or failed. At state 316C the CM 108 terminates the call with the account owner.

FIG. 3D illustrates the authentication process wherein the client application 116 executing on the terminal 110 places the authentication call and enters a password during the call. At state 302D, the user registers to open a new account. At state 304D the user/account owner downloads the client application 116 to the computer terminal 110. During another Internet session, at state 306D the account owner logs onto the Internet 106. At state 308D the client application 116 logs in with the SM 122. At state 310D the SM 122 accesses the user's account database records to determine if an authentication process needs to take place. For example, the act of establishing the account can trigger a need for the authentication process. By way of another example, if the user places an order for a good or service, such as a call handling service request as similarly discussed above, the authentication process may need to be performed.

If there is a need to authenticate, then at state 312D the SM 122 requests the client application 116 to initiate the authentication call. If the terminal 110 is using a POTs phone line to access the Internet, at state 314 the account owner or client application terminates the Internet connection. If the terminal 110 is connected to the Internet via a broadband connection, then there is no need to terminate the Internet connection. At state 316D the client application 166 calls a toll-free authentication phone number associated with the system operator or service provider. At state 318D the Call Management (CM) subsystem 108 answers the call and records the charge number (CN) and optionally the ANI (CID). At state 320D the CM 108 determines whether the CN is the same as the account phone number. If the CN is not the same as the account phone number, the phone number authentication fails. If the CN is the same as the account phone number, the phone number authentication is successful. At state 322 the client application 116 generates DTMF tones corresponding to the account owner's account number and the password.

At state 324D the CM 108 determines whether the password entered by the client application 116 matches that stored in the account owner's database record to thereby verify whether the entered password is correct. An email or other communication can be provided to the account owner to indicate whether the authentication process succeeded or failed. At state 316D the CM 108 terminates the call with the client application 116.

As illustrated in FIG. 4, in another embodiment, the user's identity is authenticated or verified as follows. At state 402, the user accesses a web site associated with the call processing system 124 via the Internet, sets up a user account, and provides contact information, including a phone number that the user indicates is the user's phone number. The user can also provide other contact information, including, by way of example, an email address, a regular address, a facsimile number, alternate phone numbers, and the like, as well as a user identifier and a user password. The contact information is stored in a user account database. At state 404, the user downloads the client application 116 from the call processing system 124.

If the user has gone offline, then at state 406 the user logs onto the Internet 106. At state 408, the client application logs in with the call processing system 124. For example, the client application 116 can transmit a unique identifier and an “I'm alive” message and subsequent periodic “keep alive” messages to the online presence detection Internet Session Management (SM) subsystem 122. At state 410, the SM 122 accesses the user's account database records to determine if an authentication process needs to take place. For example, the act of establishing the account can trigger a need for the authentication process. By way of another example, if the user places an order for a good or service, such as a call handling instruction as similarly discussed above, the authentication process may need to be performed. For example, the order or instruction can be provided via the client application 116. In other examples, the order can be provided via a website, such as the call processing service provider's website, via phone, via email, via regular mail, or the like.

At state 412, the call processing system 124 transmits over the Internet a verification code, which can be in the form of an alphanumeric password, and instructions for using the verification code, to the client application 116 which are displayed to the user at state 414 via the client application 116 or the like. The instructions for using the verification code notify the user that a call will be placed to the user asking for the verification code and once the call is received, the user should enter the password orally or by providing DTMF tones using the phone 112 keypad. The instructions include a request that the user terminate the Internet session and put the terminal 110 into an offline state if the terminal 110 is currently using the phone line. Alternatively or in addition, the client application 116 can automatically force the terminal 110 to go offline, though the client 116 application optionally requests user approval before doing so. At state 416 the Internet session is terminated and the SM 122 automatically logs out the client application 116.

At state 418 the Session Manager (SM) 122 instructs the Call Management (CM) subsystem 108 to initiate an authentication call to the corresponding user account phone number stored in the database 136. At state 420, the CM 108 places the call to the account phone number. If the user is actually at that phone number, then the user will be able to answer the phone call and provide the verification code. However, if the user gave a false phone number or somebody else's phone number, then the user who placed the order will not answer the phone call and therefore will not provide the verification code.

If the user provided a phone number accessible to the user, then at state 422 the user answers the call. If the call is not answered, the process proceeds to state 432 and the call is terminated, in which cause the order is refused or put on hold. In this case, the call processing system optionally attempts to place the call again at a later time or date. At state 424 the CM 108 requests that the user enter the verification code. At state 426, the user enters the verification code by speaking the code or by pressing the phone keypad keys to thereby provide corresponding DTMF tones. At state 428 the CM 108 compares the entered code with the verification code previously provided to the user, and if they match, the authentication is successful. During the call, at state 430 the user is verbally informed of the success or failure, and a confirmation email is optionally sent to the user. If the user has not yet terminated the call, the call processing then terminates the call at state 432.

In another embodiment, a verification process is used to activate a credit card or other service or product as follows. When a user applies or orders a service or product, such as a credit card, the user provides a first phone number associated with the user. The user is optionally then provided with a device, such as a credit card or software, needed to access the service. However, before using the device or accessing the service, the user needs to verify that the user is indeed associated with the first phone number. The user calls a verification phone number, and the network signaling is accessed to obtain the call's CN information. The CN information is compared with the first phone number, and if the comparison is successful, the device, service and/or product is activated.

Thus, as described above, embodiments of the present invention utilize telecommunication services to authenticate that a user is associated with a phone number that the user provided when placing an order or when establishing an account. Thus, embodiments of the present invention advantageously enable the reduction of fulfillment of fraudulent orders or prank orders.

It should be understood that certain variations and modifications of this invention would suggest themselves to one of ordinary skill in the art. The scope of the present invention is not to be limited by the illustrations or the foregoing descriptions thereof. 

What is claimed is:
 1. A method of authenticating a user identity using telephony signaling, comprising: accessing, at least in part, an account for a user; storing in memory account information for the user, the account information including at least a first phone number that the user is representing is associated with the user; receiving at a call processing system a call from the user, the call associated with network call signaling information, including a caller identification field and a charge phone number field, wherein the charge phone number field is not the same field as the caller identification field and wherein the charge phone number contained in the charge number field is provided by a network system and is not entered by the user; facilitating, via the call processing system, a comparison of the charge phone number information obtained from the charge phone number field with the first phone number to, at least in part, authenticate that the user is associated with the first phone number; and at least partly in response to determining that the charge phone number information obtained from the charge phone number field does not correspond to the first phone number, transferring the call to a live operator.
 2. The method as defined in claim 1, wherein the call signaling information indicates the call is from a private number.
 3. The method as defined in claim 1, the method further comprising: accessing, at least in part, a user password from the account information; facilitating, via the call processing system, a comparison of a password entered by the user and the user password accessed from the account information; and, at least partly in response to determining that the password entered by the user does not correspond to the user password accessed from the account information, transferring the call to a live operator.
 4. The method as defined in claim 3, wherein the call processing system receives dtmf tones for the password entered by the user.
 5. The method as defined in claim 3, wherein the call processing system receives a spoken password for the password entered by the user.
 6. The method as defined in claim 1, the method further comprising electronically comparing Caller identification information included in the caller identification field with the first phone number, wherein both the charge phone number information and the Caller identification information need to match the first phone number in order to provide verification that the first user is associated with the first phone number.
 7. The method as defined in claim 1, the method further comprising causing a computer terminal associated with the user to automatically place the call via an instruction transmitted over a data network to the user computer terminal.
 8. The method as defined in claim 1, wherein the call is placed by the user.
 9. The method as defined in claim 1, the method further comprising, at least partly in response to determining that the charge phone number information obtained from the charge phone number field does not correspond to the first phone number, sending an email to the user indicating a failed authentication.
 10. The method as defined in claim 1, wherein the call is associated with an activation of a credit card.
 11. A method of authenticating a user identity using telephony signaling, comprising: accessing, at least in part, an account for a user; storing in memory account information for the user, the account information including at least a first phone number that the user is representing is associated with the user; receiving at a call processing system a call from the user, the call associated with network call signaling information, including charge phone number information wherein the charge phone number is accessed from a charge number field distinct from a caller identification field and wherein the charge phone number contained in the charge number field is provided by a network system and is not entered by the user; facilitating, via the call processing system, a comparison of the charge phone number information obtained from the charge phone number field with the first phone number to, at least in part, authenticate that the user is associated with the first phone number; and at least partly in response to determining that the charge phone number information obtained from the call signaling does not correspond to the first phone number, connecting the call to a live operator.
 12. The method as defined in claim 11, wherein the call signaling information indicates the call is from a private number.
 13. The method as defined in claim 11, the method further comprising: accessing, at least in part, a user password from the account information; facilitating, via the call processing system, a comparison of a password entered by the user and the user password accessed from the account information; and, at least partly in response to determining that the password entered by the user does not correspond to the user password accessed from the account information, connecting the call to a live operator.
 14. The method as defined in claim 13, wherein the call processing system receives dtmf tones for the password entered by the user.
 15. The method as defined in claim 13, wherein the call processing system receives a spoken password for the password entered by the user.
 16. The method as defined in claim 11, the method further comprising electronically comparing Caller identification information included in the caller identification field with the first phone number, wherein both the charge phone number information and the Caller identification information need to match the first phone number in order to provide verification that the first user is associated with the first phone number.
 17. The method as defined in claim 11, the method further comprising causing a computer terminal associated with the user to automatically place the call via an instruction transmitted over a data network to the user computer terminal.
 18. The method as defined in claim 11, the method further comprising, at least partly in response to determining that the charge phone number information obtained from the charge phone number field does not correspond to the first phone number, sending an email to the user indicating a failed authentication.
 19. The method as defined in claim 11, wherein the authentication call is associated with the activation of a credit card.
 20. A call processing system comprising: at least one computing device; program instructions stored in non-transitory memory, that when executed by the at least one computing device, are configured to cause the system to perform operations comprising: accessing, at least in part, an account for a user; storing in memory account information for the user, the account information including at least a first phone number that the user is representing is associated with the user; receiving a call from the user, the call associated with network call signaling information, including charge phone number information wherein the charge phone number is accessed from a charge number field distinct from a caller identification field and wherein the charge phone number contained in the charge number field is provided by a network system and is not entered by the user; facilitating a comparison of the charge phone number information obtained from the charge phone number field with the first phone number to, at least in part, authenticate that the user is associated with the first phone number; and at least partly in response to determining that the charge phone number information obtained from the call signaling does not correspond to the first phone number, connecting the call to a live operator. 